﻿<p>
This example includes a library file containing an air terminal type. It explains how type definitions can be included from an external library. 
</p>
<p>
The air terminal type consists of a single port, with property sets defined on the type and port. Figure 506 illustrates the air 
terminal type, where a green arrow indicates the port, placed at the arrow head.
</p>
<blockquote class="note">
  NOTE&nbsp; The arrow head is not part of the exchange, only the port definition. Viewers may represent ports in different ways.
</blockquote>
<p>
  The property sets have backing templates from an external library file.
</p>
<blockquote class="note">
  Standard property sets (defined within this specification) do not require templates to be included; they are
  shown in this example for illustration, such as if custom property sets were to be used.
</blockquote>
<table summary="example of air terminal">
  <tr>
    <td>
      <img alt="example of air terminal" src="../../figures/examples/building_service_element_air-terminal-3.png" width="500">
    </td>
  </tr>
  <tr>
    <td>
      <p class="figure">Figure 506 &mdash; Air terminal type representation</p>
    </td>
  </tr>
</table>
<p>
  The type has a nested port, as illustrated in Figure 507.
</p>
<table summary="example of air terminal">
  <tr>
    <td>
      <img alt="example of air terminal" src="../../figures/examples/building_service_element_air-terminal-4.png" width="1000">
    </td>
  </tr>
  <tr>
    <td>
      <p class="figure">Figure 507 &mdash; Air terminal type object graph</p>
    </td>
  </tr>
</table>
